|
If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
Datasheet File OCR Text: |
never stop thinking. data sheet, rev. 1.21, nov. 2005 communications adm8515/x usb2.0 to 10/100 mbit/s ethernet lan controller adm8515/x
the information in this document is subject to change without notice. edition 2005-11-08 published by infineon technologies ag, st.-martin-strasse 53, 81669 mnchen, germany ? infineon technologies ag 2005. all rights reserved. attention please! the information herein is given to describe certain co mponents and shall not be considered as a guarantee of characteristics. terms of delivery and rights to technical change reserved. we hereby disclaim any and all warranties, including but not limited to warranties of non-infringement, regarding circuits, descriptions and charts stated herein. information for further information on technology , delivery terms and conditions and prices please contact your nearest infineon technologies office ( www.infineon.com ). warnings due to technical requirements components may contain da ngerous substances. for information on the types in question please contact your nearest infineon technologies office. infineon technologies components may only be used in life-support devices or systems with the express written approval of infineon technologies, if a failure of such components can reasonably be expected to cause the failure of that life-support device or system, or to affect the safe ty or effectiveness of that device or system. life support devices or systems are intended to be implanted in the hu man body, or to support an d/or maintain and sustain and/or protect human life. if they fail, it is reasonable to assume that the health of the user or other persons may be endangered. template: com_tmplt_a4 .fm / 1 / 2003-07-04 trademarks abm ? , ace ? , aop ? , arcofi ? , asm ? , asp ? , digitape ? , duslic ? , epic ? , elic ? , falc ? , geminax ? , idec ? , inca ? , iom ? , ipat ? -2, isac ? , itac ? , iwe ? , iworx ? , musac ? , muslic ? , octat ? , optiport ? , potswire ? , quat ? , quadfalc ? , scout ? , sicat ? , sicofi ? , sidec ? , slicofi ? , smint ? , socrates ? , vinetic ? , 10basev ? , 10basevx ? are registered trademarks of infineo n technologies ag. 10bases?, easyport?, vdslite? are trademarks of infi neon technologies ag. microsoft ? is a registered trademark of microsoft corporation, linux ? of linus torvalds, visio ? of visio corporation, and framemaker ? of adobe systems incorporated. usb2.0 to 10/100 mbit /s ethernet lan controller revision history: 2005-11-08, rev. 1.21 previous version: page/date subjects (major ch anges since last revision) 2003-04-10 rev. 1.0: first release of adm8515/x 2003-08-28 rev. 1.1: updated pin 5 and 6 definition 2004-05-07 rev. 1.2: updated to include infineon-admtek 2005-09-13 rev. 1.21: when changed to the new infineon format 2005-11-01 minor change. included green package information data sheet 4 rev. 1.21, 2005-11-08 adm8515/x 1 product overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.1 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.4 conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1.4.1 data lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2 interface description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.1 pin diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 2.2 pin description by function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.2.1 host interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.2.2 mii interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.2.3 physical layer interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.2.4 led display mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.2.5 eeprom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.6 regulator pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.2.7 power pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.2.8 miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 3 function description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1 usb interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.1 pie . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.1.2 ep decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2 mac controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2.1 mii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2.2 adaptive equalizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2.3 jabber and sqe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 3.2.4 auto polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.2.5 auto-negotiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.2.6 baseline wander compensation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3 fifo controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3.1 fifo controller in receive path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.3.2 fifo controller in transmit path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.4 tx fifo and rx fifo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 3.5 10/100m ethernet phy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.6 usb device endpoint operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.6.1 endpoint 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.6.2 endpoint 1 bulk in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 3.6.3 endpoint 2 bulk out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 3.6.4 endpoint 3 interrupt in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 4 registers description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.1 system registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 4.1.1 registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 4.2 phy registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 4.2.1 registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 5 usb command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.1 get register (vendor specific) single/burst read . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.2 set register (vendor specific) burst write . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 5.3 get status (device) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 5.4 get status (interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 5.5 get status (ep1) bulk in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 5.6 get status (ep2) bulk out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 5.7 get status (ep3) interrupt in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table of contents data sheet 5 rev. 1.21, 2005-11-08 adm8515/x 5.8 get descriptor (device) total 18-byte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.9 get descriptor (configuration) total 39-b yte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 5.10 get descriptor (string) index 0, languageid code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 5.11 get descriptor (string) index 1, manufa cture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.12 get descriptor (string) index 2, product . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.13 get descriptor (string) index 3, serial no. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.14 get configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 5.15 get interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.16 get descriptor (device qualifier) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.17 get descriptor (other speed co nfiguration) total 39-b yte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 5.18 clear feature (device) remote wakeup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 5.19 set feature (device) remote wakeup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.20 clear feature (ep 0, 1, 2, 3) halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.21 set feature (ep 0, 1 ,2, 3) halt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 5.22 set feature (test mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 6 electrical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.1 absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.2 operating condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.3 dc specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.3.1 usb interface dc specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 6.3.2 eeprom interface dc specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.3.3 gpio interface dc specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.4 timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.4.1 reset timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 6.4.2 eeprom interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 6.4.3 mii interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 7 packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 8 appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 8.1 appendix 1 eeprom content & example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 data sheet 6 rev. 1.21, 2005-11-08 adm8515/x figure 1 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 2 pin diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 figure 3 reference design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 figure 4 packet form when receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 figure 5 packet form when transmit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 figure 6 eeprom interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 figure 7 transmit signal timing relationships at the mii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 figure 8 received signal timing relations at the mii . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 figure 9 mdio sourced by sta . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 figure 10 mdio sourced by phy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 figure 11 p-lqfp-100-1 (plastic low profile quad flat package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 list of figures data sheet 7 rev. 1.21, 2005-11-08 adm8515/x table 1 package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 table 2 abbreviations for pin type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 table 3 abbreviations for buffer type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 table 4 host interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 5 dm and dp signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 table 6 mii interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 table 7 physical layer interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 table 8 led display mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 table 9 eeprom interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 10 regulator pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 table 11 power pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 table 12 miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 table 13 usb received status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 table 14 usb packet format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 15 interrupt packet form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 16 interrupt packet form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 table 17 registers address space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 18 registers overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 table 19 register access types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 table 20 registers clock domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 table 21 reserved registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 table 22 wakeup frame 0 mask registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 table 23 wakeup frame 1 mask registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 table 24 wakeup frame 2 mask registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 table 25 registers address space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 26 registers overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 table 27 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 table 28 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 table 29 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 table 30 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 table 31 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 32 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 33 1st out transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 34 2nd out transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 35 3rd out transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 36 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 37 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 38 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 table 39 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 40 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 41 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 42 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 43 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 44 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 45 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 table 46 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 47 data stage: wlength fiel d specifies the total byte count to return . . . . . . . . . . . . . . . . . . . . . . 71 table 48 *8/64 := usb 1.1/2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 49 *8/64 := usb 1.1/2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 50 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 51 configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 table 52 configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 53 interface 0 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 list of tables data sheet 8 rev. 1.21, 2005-11-08 adm8515/x table 54 ep1 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 55 ep2 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 56 ep3 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 57 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 58 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 table 59 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 60 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 61 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 62 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 63 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 64 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 65 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 table 66 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 67 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 68 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 69 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 70 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 71 data stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 72 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 table 73 configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 74 configuration descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 75 interface 0 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 76 ep1 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 77 ep2 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 78 ep3 descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 79 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 table 80 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 81 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 82 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 83 setup stage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 table 84 absolute maximum rating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 table 85 operating condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 table 86 usb interface dc specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 table 87 eeprom interface dc specif ication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 table 88 gpio interface dc specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 table 89 eeprom interface timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 table 90 dimensions for 100 pin lqfp package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 table 91 example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 list of tables data sheet 9 rev. 1.21, 2005-11-08 adm8515/x product overview 1 product overview the adm8515/x, usb based chip set, provides de sktop, notebook and computer peripheral with greater connectivity and data-trans mission to ethernet and home network. the adm8515x is the environmentally friendly ?green? package version. the adm8515/x device combines usb2.0 transceiver with utmi interface, an ep decoder used for usb interface through parallel interface engine (pie), fifo controller with 24k sram, 64 byte and 2k byte buffers, 10/100 mbit/s ethernet physical layer (phy) and mii interface. it is capable of providing an easy, universal connectivi ty to computer peripherals with usb. the transfer rate of usb interface is 480 mbit/s belonging to a high spee d usb device. the adm8515/x supports all usb commands, 4 endpoints and suspend/resume function. the adm8515/x?s lan phy supports 100 base tx (100 mbit/s mode) and 10 base t (10 mbit/s mode) full-duplex operations. it uses the auto-negotiati on function to optimize the network traffic and the built-in 24k bytes sram for receiving buffer, especially for 100 mbit/s. through fi fo controller, data can communicate in fluently between buffers and external device. to obtain the better signal quality, the phy provides wave -shaper, filter and adaptive equalizer to reach. by using diagno stic mechanism (loop-back mode), the data correct ness will be increased. the lan phy supports external transmit/receive transfor mer turn ratio 1:1. the adm8515/x chip set can be programmed for mac analysis and provides mii interface for external phy, such as mii interface for homepna and homeplug. in system app lication, eeprom is essentia l in that it needs to load device id, vendor id automatically. so for adm8515/x, seri al interface is applied for eeprom communication including read/write function. furthermore, some led pins report system statuses. infineon- admtek provides an eeprom access program utility for pr ogramming vendor id, product id etc. adm8515/x is ideally suited for usb adapter and intelligen t networked peripheral design. it can also be used in wide area network (wan), such as xdsl, cable modem, router, and information appliance (ia) application etc. 1.1 package information 1.2 features main features: ? industrial standard ? ieee 802.3u 100 base-tx and ieee 802. 3 10bbase-t compliant ? supports ieee 802.3x flow control ? supports ieee 802.3u auto-negotiation for 10base-t and 100base-tx ? usb specification 2.0 compliant ? usb interface ? high speed usb device ? supports 1 usb configuration and 1 interface ? supports all usb standard commands ? supports two vendor specific commands ? supports usb suspend/resume detection logic ? supports 4 endpoints: 1 control endpoint with maximu m 64-byte packet, 1 bulk in endpoint with maximum 512-byte packet, 1 bulk out endpoint with maximu m 512-byte packet and 1 interrupt in endpoint with maximum 8-byte packet ? mac/phy table 1 package information product name product type package ordering number adm8515/x adm8515/x-ac-t-1 p-lqfp-100-1 q67801h 24a101 data sheet 10 rev. 1.21, 2005-11-08 adm8515/x product overview ? integrates the whole physical la yer functions of 100 base-tx and 10base-t by using phy address 1 ? can be programmed to isolate the internal phy, supports mii interface to external 10/100 phy ? supports configurable threshold for pause frame ? supports wakeup frame, link status change and magic packet wake-up ? supports full-duplex operation on both 100 mbit/s and 10mbit/s speed modes ? supports auto-negotiation (n-way) function of fu ll/half duplex operation for both 10/100 mbit/s ? provides transmit wave-shaper, re ceives filter, an d adapter equalizer ? provides mlt-3 transceiver with dc restor ation for base-line wander compensation ? supports mac and transceiver loop back diagnostic modes ? supports external transmit/receive transformer with turn ratio 1:1 ? eeprom interface ? provides serial interface to access 93c46 eeprom ? automatically load device id, vendor id from eeprom afte r power-on reset ? fifo ? supports internal 2k bytes sram for transmission ? supports internal 24k bytes syn chronous sram for receiving ? led interface ? provides 4 led display modes ? provides usb full speed/high speed display modes ? support power save function @ usb suspend mode ? mode 0: resume by remote wakeup or host when os goes into standby ? mode 1: resume by host when os goes into standby. ? power consumption < 2.5 ma @ mode 1 ? support software ? windows 98/me/2000/xp driver ? linux driver ? wince 3.0 & 4.0 drivers ? eeprom burn-in program ? mfg testing program ? miscellaneous ? supports 6 gpio pins ? provides 100-pin lqfp package ? 3.3 v power supply with 5 v/3.3 v i/o tolerance data sheet 11 rev. 1.21, 2005-11-08 adm8515/x product overview 1.3 block diagram figure 1 block diagram 1.4 conventions 1.4.1 data lengths qword 64 bits dword 32 bits word 16 bits byte 8 bits nibble 4 bits data sheet 12 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2 interface description 2.1 pin diagram pin diagram of adm8515/x. figure 2 pin diagram data sheet 13 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2 pin description by function adm8515/x pins are categorized into one of the following groups: ? host interface ? mii interface ? physical layer interface ? led display mode ? eeprom interface ? regulator pins ? power pins ? miscellaneous table 2 abbreviations for pin type abbreviations description i standard input-only pin. digital levels. o output. digital levels. i/o i/o is a bidirectional input/output signal. ai input. analog levels. ao output. analog levels. ai/o input or output. analog levels. pwr power gnd ground mcl must be connected to low (jedec standard) mch must be connected to high (jedec standard) nu not usable (jedec standard) nc not connected (jedec standard) table 3 abbreviations for buffer type abbreviations description z high impedance pu1 pull up, 10 k ? pd1 pull down, 10 k ? pd2 pull down, 20 k ? ts tristate capability: the corr esponding pin has 3 operationa l states: low, high and high- impedance. od open drain. the corresponding pin has 2 oper ational states, active low and tristate, and allows multiple devices to shar e as a wire-or. an external pull-up is required to sustain the inactive state until another agent drives it, and must be provid ed by the central resource. oc open collector pp push-pull. the corresponding pin has 2 operational states: active-low and active-high (identical to output with no type attribute). od/pp open-drain or push-pull. the corresponding pi n can be configured either as an output with the od attribute or as an output with the pp attribute. st schmitt-trigger characteristics ttl ttl characteristics data sheet 14 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2.1 host interface table 4 host interface pin or ball no. name pin type buffer type function 8 i_clk12 i input clock 12 mhz clock input from crystal or oscillator. 7 o_clk12 o output for crystal 95 rst# i external hardware reset input schmitt trigger, internal pull high. 94 poren_n i internal power on reset logic enable default is enable and internal pull-low. when external hardware reset is used, this pin should be connected to vcc via 4.7 k ? resistor. 32 vph i/o usb d + port for high speed 30 vmh i/o usb d - port for high speed 33 vpf i/o usb d + port for full speed 31 vmf i/o usb d - port for full speed 28 rref pull down with 510 ohm precise resistor ( 1%) 35 rpu pull up with a 1.5 k ohm resistor 42 line0 o usb line state they directly reflect the current state of the dp (line1) and dm (line0) signals, see table 5 43 line1 table 5 dm and dp signals dm dp description 000: se0 0 1 1: ?j? state 1 0 2: ?k? state 113: se1 data sheet 15 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2.2 mii interface note: program adm8515/x as mac-only mode, set register 81 h [4:2] = 001 b and register 01 h bit 2 = 0 table 6 mii interface pin or ball no. name pin type buffer type function 53 col i collision detected this signal is asserted high asynchronously by the external physical unit upon detection of a collision on the medium. it will remain asserted as long as the collision condition persists. 52 crs i carrier sense this signal is asserted high asynchronously by the external physical unit upon detection of a non-idle medium. 72 mdc o management data clock clock signal with a maximum rate of 2.5 mhz used to transfer management data for the external pmd on the mdio pin. 73 mdio i/o management data i/o bi-directional signal used to transfer management information for the external pmd. requires a 1.5 k ? pull-up resistor if external phy is used. 64 rxclk i receive clock a continuous clock that is recovered from the incoming data. during 100 mbit/s operation, rxclk is 25 mhz. during 10 mbit/s, this is 2.5 mhz. 71 rxd3 i receive data this is a group of 4 data signals aligned on nibble boundary which are driven synchronous to the rxclk by the external physical unit. rxd[3] is the mo st significant bit and rxd[0] is the least significant bit. 69 rxd2 68 rxd1 67 rxd0 65 rxdv i receive data valid this indicates that the external physical unit is presenting recovered and decoded nibbles on the rxd[3:0] and that rxclk is synchronous to the recovered data 63 rxer i receive error this signal is asserted high synchronously by the external physical unit whenever it detects a media error and rxdv is asserted. if not used, it sh ould be grounded, e.g. isolate internal phy and use external phy. 62 txclk i transmit clock a continuous clock that gets its source by the physical layer. during 100 mbit/s oper ation, this clock is 25 mhz. during 10 mbit/s operation, this clock is 2.5 mhz. data sheet 16 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2.3 physical layer interface 54 txd3 o transmit data this is a group of 4 data signals which are driven synchronously to the txclk for transmission to the external physical unit. txd[3] is the most significant bit and txd[0] is the least significant bit. 55 txd2 58 txd1 59 txd0 60 txen o transmit enable this signal is synchronous to txclk and provides precise framing for data carried on txd[3:0]. it is asserted when tx[3:0] contains valid data to be transmitted. requires external pull-down resistor 4.7 k ? if external phy is used. 74 xlnksts i link status indication external phy reports link stat us information to system and level change trigger. connect to external phy?s link status report pin or pull-down to low if not used. table 7 physical layer interface pin or ball no. name pin type buffer type function 85 o_clk25 o crystal out 25 mhz 86 i_clk25 i crystal in 25 mhz 78 rxip i receives inputs the differential receives inputs of 100base-tx or 10base-t, these pins direct ly input from magnetic. 77 rxin 88 txop o transmits outputs the differential transmit s outputs of 100base-tx or 10base-t, these pins dire ctly output to magnetic. 89 txon 83 ribb i reference bias resistor to be tied to an external 10.0 k ? (1%) resistor which should be connected to the analog ground at the other end. 80 antest_a o phy test pins 81 antest_b table 6 mii interface (cont?d) pin or ball no. name pin type buffer type function data sheet 17 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2.4 led display mode the led interface is eeprom program mable, 2 eeprom control bits, addr ess ob [7:6] in eeprom are used to select the led display mode. notes 1. eeprom 0b[7:6] = 00 b led0: 100 mbit/s (on, drive '0') or 10 mbit/s (off, drive '1') led1: link (keeps on when link on) or activity (flash with 10 hz when adm8515/x is receiving or transmitting without collision) led2: full duplex (keeps on when in full duplex mode) or collis ion (flash with 20 hz when collision occurred in half duplex mode) 2. eeprom 0b[7:6] = 01 b led0: activity (flash with 10 hz when adm8515 /x is receiving or tr ansmitting without collision) led1: link 10 (keeps on when link on 10 mbit/s) led2: link 100 (keeps on when link on 100 mbit/s) 3. eeprom 0b[7:6] = 10 b led0: 100 mbit/s (on, drive '0') or 10 mbit/s (off, drive '1') led1: activity (flash with 10 hz when adm8515 /x is receiving or tr ansmitting without collision) led2: link (keeps on when link on) 4. eeprom 0b[7:6] = 11 b led0: link 10 (led on when link on 10mbit/s) and activi ty (flash with 10hz when adm8515/x is receiving or transmitting without collision)led1: li nk 100 (led on when link on 100mbit/s) and ac tivity (flash with 10hz when adm8515/x is receiving or transm itting without collision) led2: full duplex (keeps on when in full duplex mode) table 8 led display mode pin or ball no. name pin type buffer type function 1led0o function of led0 function of led0 is described below. 2led1o function of led1 function of led1 is described below. 3led2o function of led2 function of led2 is described below. 5led3o led display for usb full led display for usb full speed rate link, active high. 6led4o led display for usb high led display for usb high speed rate link, active high. data sheet 18 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2.5 eeprom interface 2.2.6 regulator pins note: adm8515/x is a dual power device , it needs both 3.3 v and 2.5 v power supply. inside the chip, there is an embedded 3.3 v to 2.5 v power regulator that can generate the needed 2.5 v power to supply the chip. the reference schematics design is shown in figure 3 table 9 eeprom interface pin or ball no. name pin type buffer type function 48 eecs o eeprom chip select this pin enables the eeprom during loading of the ethernet configuration data. 46 eedi o eeprom data in adm8515/x will use this pin to serially write opcodes, addresses and da ta into the serial eeprom. 45 eedo i eeprom data out adm8515/x will read t he contents of th e eeprom serially through this pin. 47 eesk o eeprom clock after reset, adm8515/x will auto -load the contents of the eeprom by using eesk, eedo, and eedi. this pin provides the clock for the eeprom device. table 10 regulator pins pin or ball no. name pin type buffer type function 100 vddah p chip regulator 3.3 v power supply for on chip regulator. 98 vsa p ground for regulator 99 vctrl i/o regulator control pin 97 vsense i 2.5 v voltage sense input data sheet 19 rev. 1.21, 2005-11-08 adm8515/x interface de scription figure 3 reference design 2.2.7 power pins table 11 power pins pin or ball no. name pin type buffer type function 12, 41, 57 vdd25 p 2.5 v power supply for core 13, 40, 56 vss25 p ground for vdd25 4, 49, 61, 70, 96 vddio p 3.3 v power supply for i/o 22, 44, 51, 66, 93 vssio p ground for vddio 26 dvdd1 p 2.5 v digital power supply 39 dvdd2 36 dgnd1 p digital ground 38 dgnd2 27 avdd1 p 3.3 v analog power supply 34 avdd2 29 agnd1 p analog ground 37 agnd2 90 vaat p 3.3 v power supply for transmitter 87 gndt p ground for vaat 76 vaar p 3.3 v power supply for receiver 79 gndr p ground for vaar 84 vaaref p 3.3 v power supply for phy 82 gndref p ground for vaaref data sheet 20 rev. 1.21, 2005-11-08 adm8515/x interface de scription 2.2.8 miscellaneous table 12 miscellaneous pin or ball no. name pin type buffer type function 19 gpio5 i/o general purpose input/output pins these pins are used as general purpose input/output pins. these pins are internal pull-low. 20 gpio4 21 gpio3 23 gpio2 24 gpio1 25 gpio0 92, 91 test 1 i test pins 9, 10, 11, 14, 15, 16, 17, 18 test2 i/o test pins data sheet 21 rev. 1.21, 2005-11-08 adm8515/x function description 3 function description 3.1 usb interface usb is a straightforward solution when you want to us e a computer for communication with devices outside the computer. the interface is suitable for one-of-kind and small-scale designs as well as mass-produced, standard peripheral. the be nefits of usb are easy to use a nd easy to apply, fast and reliabl e data transfers, flexibility, cost, and power conservation. 3.1.1 pie pie (parallel interface engine) is to control usb communications an d check usb protocol, then transfer protocol to ep decoder. the pie and usb transceivers, which prov ide the hardware interface to the usb cable, together comprise the usb engine. 3.1.2 ep decoder the detail description is in section 4.5 usb command. 3.2 mac controller 3.2.1 mii the media independent interface (mii) is an 18 wire mac/ phy interface described in 802.3u. the purpose of the interface is to allow mac layer devi ces to attach to a variety of phys ical layer devices through a common interface. mii operates at 100 mbit/s or 10 mbit/s, dependant on the speed of the physical layer. with clocks running at either 25 mhz or 2.5 mhz, 4 bit data is clocked between the mac and phy, synchronous with enable and error signals. on receipt of valid data fr om the wire interface, rx_dv will go active si gnaling to the mac that the valid data will be presented on the rxd[3:0] pi ns at the speed of the rx_clk. on transmission of data from the mac, tx_en is presented to the phy indi cating the presence of valid data on txd[3:0]. txd[3:0] are sampled by the phy synchronous to tx_clk during the time that tx_en is valid. 3.2.2 adaptive equalizer the amplitude and phase distortion from a cable causes inter-symbol inte rference (isi) which makes clock and data recovery difficult. the adaptive equalizer is designe d to closely match the inverse transfer function of the twisted-pairs cable. the equa lizer has the ability to change its equalizer freq uency response acco rding to the cable length. the equalizer will tu ne itself automatically fo r any cable, compensating for the amplitude and phase distortion introduced by the cable. 3.2.3 jabber and sqe after the mac transmitter exceeds the jabber timer, the transm it and loop back function s will be disabled and col signal gets asserted. after tx _en goes low for more than 500 ms, the tp transmitte r will reactivate and col gets de-asserted. setting ja bber disable will disabl e the jabber function. when the sqe test is enabled, a col pulse is asse rted after each transmitted packet. sqe is enabled in 10base-t by default. data sheet 22 rev. 1.21, 2005-11-08 adm8515/x function description 3.2.4 auto polarity certain cable plants have crossed wiring on the twiste d pairs; the reversal of txin and txip. under normal circumstances this would cause the receiv e circuitry to reject all data. when the auto polarity disable bit is cleared, the phy has the ability to detect the fact that either 8 normal link pulses (nlp) or a burst of flps are inverted and automatically reverse the receiver ?s polarity. the polarity state is stored in the reverse polarity bit. 3.2.5 auto-negotiation it provides a linked device with the ca pability to detect the abilit ies (modes of operations) supported by the device at the other en d of the link, determine common abilities, and configure for joint operation. auto-negotiation is performed out-of-band usin g a pulse code sequence th at is compatible with t he 10base-t link integrity test sequence. 3.2.6 baseline wander compensation the 100base-tx data stream is not always dc balanced . the transformer blocks t he dc components of the incoming signal, thus the dc offset of the differential rece ive inputs can drift. the shifting of the signal level, coupled with non-zero rise and fall times of the serial st ream can cause pulse-width di stortion. this creates jitter and possible increase in the bit error rates. therefore, a dc restoration circuit is needed to compensate for the attenuation of the dc component. un like the traditional impl ementation, the circuit does not need the feedback information from the slicer or the cl ock recovery circuit. the design simplif ies the circuit design. in 10base-t, the baseline wander correction circuit is not required. 3.3 fifo controller 3.3.1 fifo controller in receive path ? store received ethernet packets to sram (internal 24 kbyte) and total 16 packets can be stored to sram. if more than 16 packets are received or total packet size is more than 24 kbytes, the subsequent coming ethernet packet will be discarded. ? fifo controller will load data from sram to internal rx fifo then inform ep decoder that 512-byte data or a packet is ready in rx fifo . before fifo controller in forms about this, any usb access to bulk in endpoint will return nak. this is to maintain the data transfer on usb bus via bulk in transfer is continuous, thus a 512-byte internal rx fifo is needed. ? if an ethernet packet is being received and loading into sram while fifo cont roller is moving data from sram to internal rx fifo, writing the ethern et packet to sram will get the higher priority. 3.3.2 fifo controller in transmit path ? store each individual usb packet to internal tx fifo. when ep decoder informs end of packet, a complete ethernet packet is stored in tx fifo. fifo controller then inform s mac to transmit this packet. ? total 4 ethernet packets can be stored in tx fifo. if all 4 ethernet packets are stored in tx fifo or total packet size is more than 2 kbytes, fifo controller will inform ep decoder that tx fifo is full and ep decoder will return nak if accessing to bulk out endpoint is invoked. thus addi tional usb packet won?t be written into tx fifo until tx fifo has free space. 3.4 tx fifo and rx fifo rx fifo is a one-port 512 byte fifo an d tx fifo is a two-port 2 kbyte fifo data sheet 23 rev. 1.21, 2005-11-08 adm8515/x function description 3.5 10/100m ethernet phy the ethernet phy is compli ant to ieee 802.3u 100base-tx and ieee 802.3 10base-t. it pr ovides the whole physical layer functions for bo th 10m and 100m ethernet speed. 3.6 usb device endpoint operation 3.6.1 endpoint 0 endpoint 0 is in charge of response to standard usb co mmands and vendor specific commands. internal register settings are also via this endpoint 0. the resp onse to each command is described in ?usb commands?. 3.6.2 endpoint 1 bulk in endpoint 1 is in charge of sending th e received ethernet packet to usb host. an ethernet packet will be split to multiple 512 bytes usb packets on usb. the end of the et hernet packet is indicated by less then 512 byte or 0 length data transfer in this pipe. the ethernet received status is optionally reported at the end of the packet. while accessing to this endpoint, if rxfifo is either full or any packet is inside, the data in rxfifo is returned in usb data stage. if ack is received from usb host, data in rxfifo is flushed. if no response or nak is received from usb host, the content in rxfifo will be re-transmitted. if rxfifo isn?t ready for transmission, nak is returned to usb host. figure 4 packet form when receive the received status is reported as follows: table 13 usb received status offset bit field description offset0 7-0 rx_bytecnt_lo the received byte count[7:0]. offset1 3-0 rx_bytecnt_hi the received byte count[11:8]. 7-4 reserved offset2 0 multicast_frame indicat es received multicast frame. 1 long_pkt indicates received packet length > 1518 bytes. 2 runt_pkt indicates received packet length < 64 bytes. 3 crc_err indicates crc check error. 4 dribble_bit indicates packet length is not integer multiple of 8- bit. 7-5 reserved offset3 7-0 reserved data sheet 24 rev. 1.21, 2005-11-08 adm8515/x function description 3.6.3 endpoint 2 bulk out endpoint 2 is in charge of sending the usb packet to ethernet. an ethernet packet is concatenated by multiple 512 bytes usb packets on usb. the first two bytes in ev ery first concatenated usb pa cket indicate the length of the ethernet packet. the end of the ethernet packet is indica ted by less then 512-byte or 0 length data transfer in this pipe. the ethernet transmit status is reported in transmit status register. when access to this endpoint, data in usb data stage ar e transferred to txfifo, if txfifo is free and ack is returned. if txfifo isn? t free, nak is returned. figure 5 packet form when transmit 3.6.4 endpoint 3 interrupt in endpoint 3 is in charge of returning the current et hernet transfer status every po lling interval. when access to this endpoint, 8 bytes data is returned to usb host. the 8-by te packet contains the following in the tables below: table 14 usb packet format field 1st byte in 1st usb packet 2nd byte in 1st usb packet the following packets content len[7:0]: low byte ethernet packet length {reserved[4:0], len[10 :8]} ethernet packet table 15 interrupt packet form offset0 offset1 offset2 offset3 offset4 tx_status(reg2b h ) tx_status(reg2c h ) rx_status(reg2d h ) rx_lostpkt(reg2e h ) rx_lostpkt(reg2f h ) table 16 interrupt packet form offset5 offset6(1b) offset7(1b) wakeup_status(reg7a h ) packet number in rx fifo (reg82 h ) 7?b00, length error data sheet 25 rev. 1.21, 2005-11-08 adm8515/x registers descriptionsystem registers 4 registers description 4.1 system registers table 17 registers address space module base address end address note 0000 0000 h 0000 0082 h table 18 registers overview register short name register long name offset address page number ec0 ethernet control 0 00 h 28 ec1 ethernet control 1 01 h 29 ec2 ethernet control 2 02 h 30 res0 reserved 0 03 h 31 res1 reserved 1 04 h 31 res2 reserved 2 05 h 31 res3 reserved 3 06 h 31 res4 reserved 4 07 h 31 ma0 multicast address 0 08 h 32 ma1 multicast address 1 09 h 32 ma2 multicast address 2 0a h 33 ma3 multicast address 3 0b h 33 ma4 multicast address 4 0c h 34 ma5 multicast address 5 0d h 34 ma6 multicast address 6 0e h 35 ma7 multicast address 7 0f h 35 eid0 ethernet id 0 10 h 36 eid1 ethernet id 1 11 h 36 eid2 ethernet id 2 12 h 37 eid3 ethernet id 3 13 h 37 eid4 ethernet id 4 14 h 38 eid5 ethernet id 5 15 h 38 res5 reserved 5 16 h 31 res6 reserved 6 17 h 31 pt pause timer 18 h 39 res7 reserved 7 19 h 31 rpnbfc receive packet number based flow control 1a h 39 orfbfc occupied receive fifo based flow control 1b h 40 ep1c ep1 control 1c h 40 res8 reserved 8 1d h 31 adm8515/x registers descriptionsystem registers data sheet 26 rev. 1.21, 2005-11-08 bist bist 1e h 40 res9 reserved 9 1f h 31 eepromo eeprom offset 20 h 41 eepromdl eeprom data low 21 h 41 eepromdh eeprom data high 22 h 42 eepromac eeprom access control 23 h 43 res10 reserved 10 24 h 31 phya phy address 25 h 43 phydl phy data low 26 h 44 phydh phy data high 27 h 44 phyac phy access control 28 h 45 res11 reserved 11 29 h 31 usbbs usb bus status 2a h 45 ts1 transmit status 1 2b h 45 ts2 transmit status 2 2c h 47 rs receive status 2d h 47 rlpch receive lost packet count high 2e h 48 rlpcl receive lost packet count low 2f h 48 wuf0m_0 wakeup frame 0 mask 30 h 48 wuf0m_1 wakeup frame 0 mask 1 31 h 49 ... ... ... h 49 wuf0m_xx wakeup frame 0 mask xx 3f h 49 wuf0o_0 wakeup frame 0 offset 40 h 49 wuf0crcl wakeup frame 0 crc low 41 h 50 wuf0crch wakeup frame 0 crc high 42 h 50 res12 reserved 12 43 h 31 res13 reserved 13 44 h 31 res14 reserved 14 45 h 31 res15 reserved 15 46 h 31 res16 reserved 16 47 h 31 wuf1m_0 wakeup frame 1 mask 48 h 51 wuf1m_1 wakeup frame 1 mask 1 49 h 51 ... ... ... h 51 wuf1m_xx wakeup frame 1 mask xx 57 h 51 wuf1o wakeup frame 1 offset 58 h 51 wuf1crcl wakeup frame 1 crc low 59 h 52 wuf1crch wakeup frame 1 crc high 5a h 52 res17 reserved 17 5b h 31 res18 reserved 18 5c h 31 res19 reserved 19 5d h 31 res 20 reserved 20 5e h 31 table 18 registers overview (cont?d) register short name register long name offset address page number data sheet 27 rev. 1.21, 2005-11-08 adm8515/x registers descriptionsystem registers the register is addressed wordwise. res 21 reserved 21 5f h 31 wuf2m wakeup frame 2 mask 60 h 53 wuf2m_1 wakeup frame 2 mask 1 61 h 53 ... ... ... h 53 wuf2m_xx wakeup frame 2 mask xx 6f h 53 wuf2o wakeup frame 2 offset 70 h 53 wuf2crcl wakeup frame 2 crc low 71 h 54 wuf2crch wakeup frame 2 crc high 72 h 54 res 22 reserved 22 73 h 31 res 23 reserved 23 74 h 31 res 24 reserved 24 75 h 31 res 25 reserved 25 76 h 31 res 26 reserved 26 77 h 32 wuc wakeup control 78 h 55 res 27 reserved 27 79 h 32 wus wakeup status 7a h 56 iphyc internal phy control 7b h 56 gpio54c gpio[5:4] control 7c h 57 res 28 reserved 28 7d h 32 gpio10c gpio[1:0] control 7e h 58 gpio32c gpio[3:2] control 7f h 59 test test 80 h 60 tm test mode 81 h 60 rpn receive packet number 82 h 61 res 29 reserved 29 83 h 32 ... ... ... h 32 res xx reserved xx ff h 32 table 19 register access types mode symbol description hw description sw read/write rw register is used as input for t he hw register is readable and writable by sw read r register is written by hw (register between input and output -> one cycle delay) value written by software is ignored by hardware; that is, software may write any value to this field without affecting hardware behavior (= target for development.) read only ro register is set by hw (register between input and output -> one cycle delay) sw can only read this register read virtual rv physically, there is no new register, the input of the signal is connected directly to the address multiplexer. sw can only read this register table 18 registers overview (cont?d) register short name register long name offset address page number adm8515/x registers descriptionsystem registers data sheet 28 rev. 1.21, 2005-11-08 4.1.1 registers ethernet control 0 latch high, self clearing lhsc latch high signal at high level, clear on read sw can read the register latch low, self clearing llsc latch high signal at low-level, clear on read sw can read the register latch high, mask clearing lhmk latch high signal at high level, register cleared with written mask sw can read the register, with write mask the register can be cleared (1 clears) latch low, mask clearing llmk latch high signal at low-level, register cleared on read sw can read the register, with write mask the register can be cleared (1 clears) interrupt high, self clearing ihsc differentiate the input signal (low- >high) register cleared on read sw can read the register interrupt low, self clearing ilsc differentiate the input signal (high- >low) register cleared on read sw can read the register interrupt high, mask clearing ihmk differentiate the input signal (high- >low) register cleared with written mask sw can read the register, with write mask the register can be cleared interrupt low, mask clearing ilmk differentiate the input signal (low- >high) register cleared with written mask sw can read the register, with write mask the register can be cleared interrupt enable register ien enables the interrupt source for interrupt generation sw can read and write this register latch_on_reset lor rw register, value is latched after first clock cycle after reset register is readable and writable by sw read/write self clearing rwsc register is used as input for the hw, the register will be clea red due to a hw mechanism. writing to the register generates a strobe signal for the hw (1 pdi clock cycle) register is readable and writable by sw. table 20 registers clock domains clock short name description ec0 offset reset value ethernet control 0 00 h 09 h table 19 register access types (cont?d) mode symbol description hw description sw u z 7 ; ( u z 5 ; ( u z 5 ; ) & |